Skip to content

frontend: pod: Add quick status for containers #3008

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Conversation

skoeva
Copy link
Collaborator

@skoeva skoeva commented Mar 21, 2025

This change adds a new icon displaying the status of each container in the pods list. Hovering over the icon gives important info about the container at a glance: name, status, reason, exit code, and start/finish times.

Fixes: #2689

Testing

  • Navigate to the Pods page in Headlamp
  • Note the container status icon, and hover over to see additional info about the container

image

image

@skoeva skoeva added kind/feature Categorizes issue or PR as related to a new feature. frontend Issues related to the frontend labels Mar 21, 2025
@skoeva skoeva self-assigned this Mar 21, 2025
@skoeva skoeva linked an issue Mar 21, 2025 that may be closed by this pull request
@dosubot dosubot bot added the size:L This PR changes 100-499 lines, ignoring generated files. label Mar 21, 2025
@sniok
Copy link
Collaborator

sniok commented Mar 21, 2025

There are some cases where status column and new containers column have different colors for the same status which can be a bit confusing

image

Also maybe we can move container status indicators into Status column?

@skoeva skoeva force-pushed the container-status branch 3 times, most recently from 50dd211 to 1e91f3b Compare March 21, 2025 18:47
This change adds a new icon displaying the status of each container in
the pods list. Hovering over the icon gives important info about the
container at a glance: name, status, reason, exit code, and start/finish
times.

Fixes: #2689

Signed-off-by: Evangelos Skopelitis <[email protected]>
@skoeva skoeva force-pushed the container-status branch from 1e91f3b to ced7c37 Compare March 24, 2025 15:06
@k8s-triage-robot
Copy link

Unknown CLA label state. Rechecking for CLA labels.

Send feedback to sig-contributor-experience at kubernetes/community.

/check-cla
/easycla

Copy link

CLA Not Signed

@k8s-ci-robot k8s-ci-robot added the cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. label Apr 1, 2025
@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 9, 2025
@k8s-ci-robot
Copy link
Contributor

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Copy link
Collaborator

@illume illume left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please rebase? (now that we can push to branches again)

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: skoeva
Once this PR has been reviewed and has the lgtm label, please assign joaquimrocha for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. frontend Issues related to the frontend kind/feature Categorizes issue or PR as related to a new feature. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size:L This PR changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add quick status for each container (design TBD)
5 participants